Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hand Me That Task #546

Merged
merged 5 commits into from
Feb 21, 2019
Merged

Hand Me That Task #546

merged 5 commits into from
Feb 21, 2019

Conversation

justinhart
Copy link
Member

This is an attempt to address everyone's concerns from #528

  1. This is put into Stage 2, as it is difficult.
  2. Gestures are now not the only way to succeed. Language is also a route.
  3. The task is more free-form, and is a race to do as many items as possible, similar to in Storing Groceries.

@justinhart justinhart requested review from kyordhel and johaq February 6, 2019 06:04
@justinhart justinhart changed the title Add new Hand Me That task, which is a spinoff from prior I Want This … Hand Me That Task Feb 6, 2019
Copy link
Member

@johaq johaq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the structure of the test a lot now. My main concern is that setup is too complicated for the scenario slots. I think it needs to be simplified.

scoresheets/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
@justinhart
Copy link
Member Author

justinhart commented Feb 7, 2019 via email

@johaq
Copy link
Member

johaq commented Feb 7, 2019

Sounds good to me

Copy link
Contributor

@kyordhel kyordhel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the test but I find it hard to understand and very exploitable

My major concern is that color thingy. I'm against banning color descriptors since we have categories. I can have the fuchsia IKEA cup next to a red paprika and a red apple in a group. Asking red is kinda pointless and would provide no real information and automatically discards 400pts. Instead, the robot may (blindly) ask if the object is fruit (or the category) and in a lucky strike finds the apple. The same applies for center, left, and right in groups of 3 objects. Is very exploitable.

For this reason I'm suggesting a rule to allow the operator to reply a dunno 'bout dat when the referee finds that the robot is discarding options blindly. I would also suggest that the operator only answers yes or no but I don't want to clamp interaction using NLP. Some innovative solutions might come from there.

So far my 2 cents

scoresheets/HandMeThat.tex Outdated Show resolved Hide resolved
scoresheets/HandMeThat.tex Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Outdated Show resolved Hide resolved
tasks/HandMeThat.tex Show resolved Hide resolved
@justinhart
Copy link
Member Author

I think that my updates address all of your concerns.

Copy link
Member

@johaq johaq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the changes. Task seems pretty good to me now.
Requested one change. See above.

@@ -47,8 +51,9 @@ \subsection{Additional rules and remarks}
\begin{enumerate}
\item \textbf{Keep going:} The robot should keep trying to determine the referred to object until they score or run out of time.
\item \textbf{Pass:} The robot may say pass to try the next object.
\item \textbf{Touch:} The robot may ask the referee may pick up or touch the object by saying \textit{pick up} or \textit{touch}. If the robot does this, identifying the object is worth only 100 points.
\item \textbf{Oops:} Incorrect guesses reduce the value of the correct guess by 200 points, each, but cannot make the value of the correct guess go below 100 points.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should not get points past the fourth guess. Teams could just have their robot literally guess all 30 possible objects and score 100 points.
Personally, as a referee I would not give points to a robot that is just rattling off guesses anyway but I still think it should be clear in the rules.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that the rules tweak that I made fixes this. Let me know what you think.

@johaq
Copy link
Member

johaq commented Feb 21, 2019

Looks good

johaq
johaq previously approved these changes Feb 21, 2019
kyordhel
kyordhel previously approved these changes Feb 21, 2019
@kyordhel kyordhel dismissed stale reviews from johaq and themself via c4f6cfb February 21, 2019 11:05
@kyordhel kyordhel merged commit b4ca9b9 into 2019/restructure Feb 21, 2019
@kyordhel kyordhel deleted the 2019/tasks/HandMeThat branch February 21, 2019 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants